<?xml version="1.0" encoding="UTF-8" ?>
<st:repository xsi:schemaLocation="urn:com:dassault_systemes:settings settings.xsd" xmlns:st="urn:com:dassault_systemes:settings" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:com:dassault_systemes:settings">

	<st:Description name="GeneralFind" PrimaryTabpage="/General/Find">
		<st:role>Setting to manage Find command and Power Input options</st:role>
		<st:RepositoryFile>GeneralFind</st:RepositoryFile>
		<st:version>1</st:version>
		<st:compatibility>
			<st:FullCompatibilityfromLevel>1</st:FullCompatibilityfromLevel>
			<st:UpwardCompatibilityfromLevel>1</st:UpwardCompatibilityfromLevel>
		</st:compatibility>
		<st:DedicatedController>
			<st:Framework_CPP>CATIAApplicationFrame</st:Framework_CPP>
			<st:Interface_CPP>CATICafSearchSettingAtt</st:Interface_CPP>
			<st:Framework_IDL>CATIAApplicationFrame</st:Framework_IDL>
			<st:Interface_IDL>CATIASearchSettingAtt</st:Interface_IDL>
			<st:LateType>CATCafSearchSettingCtrl</st:LateType>
		</st:DedicatedController>
	</st:Description>
	
	<st:attributes>
	
		<st:attribute Name="Prefix">
			<st:role>Default prefix implicitely used in Power Input</st:role>
			<st:detailedRole>Prefix to be used by default at the beginning of the string entered in Power Input
if none has been explicitly typed.
For example, choose c: if you use Power Input mainly to start commands,
this will avoid typing "c:" before each command name.</st:detailedRole>
			<st:string size="1">
				<st:enum>
					<st:role>none</st:role>
					<st:value>none</st:value>
					<st:role>last entered</st:role>
					<st:value>last</st:value>
					<st:role>command</st:role>
					<st:value>c</st:value>
					<st:role>favorite</st:role>
					<st:value>f</st:value>
					<st:role>type</st:role>
					<st:value>t</st:value>
					<st:role>name</st:role>
					<st:value>n</st:value>
					<st:role>NAME (name case sensitive)</st:role>
					<st:value>Name_CAP</st:value>
					<st:role>name in graph</st:role>
					<st:value>graph</st:value>
					<st:role>NAME IN GRAPH (name in graph case sensitive)</st:role>
					<st:value>NameInGraph_CAP</st:value>
					<st:role>set</st:role>
					<st:value>s</st:value>
					<st:role>SET (set case sensitive)</st:role>
					<st:value>Set_CAP</st:value>
					<st:role>color</st:role>
					<st:value>col</st:value>
					<st:role>visibility</st:role>
					<st:value>vis</st:value>
					<st:role>layer</st:role>
					<st:value>l</st:value>
					<st:role>dashed</st:role>
					<st:value>d</st:value>
					<st:role>weight</st:role>
					<st:value>w</st:value>
					<st:role>symbol</st:role>
					<st:value>symb</st:value>
				</st:enum>
				<st:default>
					<st:value>none</st:value>
				</st:default>
			</st:string>
		</st:attribute>
		
		<st:attribute Name="ContextScope">
			<st:role>Default search scope implicitely used in Power Input</st:role>
			<st:detailedRole>Context scope to be used by default for search queries entered in Power Input
if none has been explicitly typed.
For example, choose InWorkbench if you search mainly in the active element,
this will avoid typing ",in" after each criterion.</st:detailedRole>
			<st:int>
				<st:enum>
					<st:role>Everywhere</st:role>
					<st:value>0</st:value>
					<st:role>InWorkbench</st:role>
					<st:value>1</st:value>
					<st:role>FromWorkbench</st:role>
					<st:value>2</st:value>
					<st:role>FromSelection</st:role>
					<st:value>3</st:value>
					<st:role>VisibleOnScreen</st:role>
					<st:value>4</st:value>
				</st:enum>
				<st:default>
					<st:value>1</st:value>
				</st:default>
			</st:int>
		</st:attribute>
		
		<st:attribute Name="ContextPriority">
			<st:role>Flag to use the Default search scope when a favorite query is typed in Power Input</st:role>
			<st:detailedRole>Check this option to supersede the genuine context associated with a favorite query by the default context scope
when this favorite query is typed in Power Input.</st:detailedRole>
			<st:boolean>
				<st:default>
					<st:value>false</st:value>
				</st:default>
			</st:boolean>
		</st:attribute>
		
		<st:attribute Name="DeepSearch">
			<st:role>Flag to activate or deactivate the Deep search option in Find queries</st:role>
			<st:detailedRole>Check this option to activate the Deep search option in Find queries.
Then, documents in visualization mode will be transiently loaded in order to find elements.</st:detailedRole>
			<st:boolean>
				<st:default>
					<st:value>false</st:value>
				</st:default>
			</st:boolean>
		</st:attribute>

		<st:attribute Name="MaxDisplay">
			<st:role>Maximum number of elements that can be displayed in the Search results page</st:role>
			<st:detailedRole>Displaying too many lines can stick more or less the results list so it is recommended to limit this number.
Set this number to 0 if you don't want any limitation and always want all the elements to be displayed.</st:detailedRole>
			<st:uint>
				<st:min>0</st:min>
				<st:max>5000</st:max>
				<st:step>10</st:step>
				<st:default>
					<st:value>100</st:value>
				</st:default>
			</st:uint>
		</st:attribute>

		<st:attribute Name="MaxPSO">
			<st:role>Maximum number of elements that can be pre-highlighted</st:role>
			<st:detailedRole>Pre-highlighting too many elements can stick the session so it is strongly recommended to limit this number.
Set this number to 0 if you don't want any limitation and always want all the elements to be pre-highlighted.</st:detailedRole>
			<st:uint>
				<st:min>0</st:min>
				<st:max>5000</st:max>
				<st:step>10</st:step>
				<st:default>
					<st:value>1000</st:value>
				</st:default>
			</st:uint>
		</st:attribute>

	</st:attributes>
		
</st:repository>
